-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(query): reverse tracing #9319
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Skipped Deployments
|
255d821
to
f86b92f
Compare
New dependencies detected. Learn more about Socket for GitHub ↗︎
|
…ixes in a repo where we may have multiple tsconfigs
|
||
let mut parser = Parser::new_from(Capturing::new(lexer)); | ||
pub async fn reverse_trace(mut self) -> TraceResult { | ||
let files = match globwalk::globwalk( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd love at some point to combine the glob walking and the import resolution so that we can have more concurrency. Right now we have to walk the entire repo, then do the import resolution step.
Description
Implements an MVP of reverse tracing. Basically goes through all the JavaScript/TypeScript files in the repo, checks which ones import the reverse traced file, and returns those. Does this concurrently with a
JoinSet
.Also adds code to detect if a tsconfig is in scope for a file and if so, add it to the resolver. That way custom aliases work.
Testing Instructions
Added some tests including a monorepo setup with tsconfigs in the packages that define aliases